report-failure-as-issue was treating many non-agent failures as agent_failure because generic classification was always added on job failure. That made category filters noisy, especially for infra/transient failure modes where existing specific categories already exist.

• Failure classification tightening

  • Updated buildFailureMatchCategories(...) in handle_agent_failure.cjs to emit agent_failure only as a fallback.
  • agent_failure is now added only when:
    • conclusion is failure,
    • not timed out, and
    • no specific category has already been detected.

• Category-filter behavior alignment

  • This preserves existing specific categories (for example inference_access_error, report_incomplete, awf_firewall_startup_failed) as the primary signal used by report-failure-as-issue include/exclude filters.
  • Result: include filters like ["agent_failure"] no longer match infra-classified failures just because the job failed.

• Targeted test updates

  • Added/updated tests to assert:
    • agent_failure is omitted when specific categories are present.
    • infra-classified failures are skipped by include-only ["agent_failure"] filters.

// Before: generic category added alongside specific categories
if (options.agentConclusion === "failure" && !options.isTimedOut) {
  categories.push("agent_failure");
}

// After: generic category only when no specific classification exists
const hasSpecificFailureCategory = categories.length > 0;
if (options.agentConclusion === "failure" && !options.isTimedOut && !hasSpecificFailureCategory) {
  categories.push("agent_failure");
}